This PR adds IAC for provisioning infrastructure that runs a RedwoodJS console container within an AWS ECS cluster. It also updates CI/CD workflows to build and publish these images.

The purpose of these changes is to allow the existence of a bastion-like facility in AWS deployment environments, which is especially useful for running database migrations without needing to expose databases in these environments to the public internet. ECS was chosen as the compute service instead of EC2 mainly for two reasons:

1. We have existing patterns (in the usdr-gost repo) for serving this type of use-case with ECS tasks.
2. As a more serverless type of offering, ECS affords lower management overhead for the infrastructure (e.g. no OS updates to apply).

In the future, we might explore ways to manage Prisma migrations using Lambda, which would require even less management overhead and would also be much cheaper. However, support for running Prisma commands in a library-based, programmatic manner is limited, and using Lambda functions to run Prisma migrations is explicitly not recommended in their documentation. This by no means should bar us from exploring this option, but in the interest of expediency, using ECS seems like a decent solution in the meantime.